Instance scan check to identify slow jobs in transaction logs. #128
Conversation
|
Thanks for your contribution. Looks like a good instance scan. But it seems you've modified the wrong readme.md file. |
@niamccash Sure, I will change it as per your suggestion. Thank you! |
As suggested, I have added the below to the root.README.md folder: ### Instance scan check to identify slow jobs in transaction logs. ### Purpose The Instance Scan Check is a table check scan that allows administrators to investigate transaction logs in ServiceNow to diagnose performance issues reported by users. This check specifically identifies transactions with a **Response Time** greater than **120 seconds**, helping to uncover performance bottlenecks, understand user behavior, and track down issues within a specific time frame.
|
@niamccash, I have updated the READMe.md file as per your advice, could you please check if it looks good? Thank you so much for your kind support and for your feedback. |
|
Great! Thanks for updating! |
|
@niamccash Thank you so much for merging it:) |
Purpose:
This Instance Scan Check is a table check scan that enables administrators to investigate transaction logs in ServiceNow to diagnose performance issues reported by users. This check specifically identifies transactions with a Response Time greater than 120 seconds, helping to uncover performance bottlenecks, understand user behavior, and track down issues within a specific time frame.
In our organization, this check has proven extremely valuable, especially when addressing slow performance in our DEV instance. By analyzing the transaction logs, we were able to pinpoint and resolve critical issues, significantly improving overall system performance.